STEP A: Database Record Clearance

  1. Connect securely to CyberArk and establish a session per standard access controls.
  2. Open DBeaver and select the target database from the top menu when prompted.
  3. Open the script file: AMNY-Queries.sql
    Relevant function call 
    select clear_airtel_money('<TRANSACTION_REFERENCE>');

    i Replace the placeholder with the exact transaction reference for the single record being cleared at a time.

  4. Select the database TZ-MSB-PR-DB from the connection list or top menu in DBeaver before execution.
  5. Execute for one reference at a time, confirm success, and repeat for each additional reference as needed, then capture a completion screenshot for the ticket.
  6. Common issues & fixes
    ! Query failed/permission denied: verify DB user permissions and target DB; Transaction not found: validate reference; Connection lost: check VPN/network or restart DBeaver and reconnect.

STEP B: Pod Management for Util Service

  1. Connect to CyberArk again to get system access for the container environment.
  2. SSH into the container host and activate the environment profile: 
    ssh cont160150
source tz-msb-prod
    Context check

    i If source tz-msb-prod is not found, ensure the profile exists and points to the correct kubectl context or switch contexts explicitly.

  3. List util pods and pick the target: 
    pods | grep util

    i Copy the pod name from the output to reduce typos in subsequent commands.

  4. Send logs from the chosen pod if required by operations: 
    send <POD-NAME>
  5. Delete the util pod to trigger a restart via the controller: 
    kubectl delete pod <POD-NAME>

    i Wait about a minute for termination and recreation; confirm with kubectl get pods before closing the task.

  6. Common issues & fixes
    ! No pod found: repeat pods | grep util and verify context; Unauthorized: re-source env and confirm RBAC; Pod deletion hangs: check cluster health with kubectl get nodes, wait, or retry.

Notes & Tips

Aliases and contexts

i Commands like pods, logs, and send may be shell aliases; substitute with explicit kubectl commands and confirm current context as needed.

Collapsible help

i Details/summary provides accessible toggles for advanced tips; keep summary labels concise and descriptive per MDN guidance for predictable behavior across assistive tech.

Sticky navigation

i The left TOC uses CSS position: sticky with a top offset, so it remains visible while scrolling within its container on modern browsers.